Deploy preview: https://deploy-preview-13398--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 57a4e78

I'm hesitating between reexporting the container like I'm currently doing (), or exporting them with a pro suffix .

Sorry but I don't understand the difference 😆

Sorry but I don't understand the difference 😆

😅 Effectively, I copy pasted the same

• ResponsiveChartContainer: current solution (same naming but component with a watermark)
• ResponsiveChartContainerPro: other solution (different naming but only user-facing difference is the watermark)

We should probably follow what the other packages do

But I noticed each package does a different thing 😅

I would probably go with the DataGrid solution if we want to always load the new functionalities on the Pro package. This means disallowing the use of ResponsiveChartContainer

If people need to use the pro version (which is the case here), I'd keep the Pro suffix to avoid confusion and somehow prevent users from user the community one.

But I noticed each package does a different thing 😅

Yeah, it's hard to be 100% consistent on this topic, the trade-off vary greatly across the packages.
Calling the grid DataGrid on all the packages would not be nice, but on the other hand calling the range picker DateRangePickerPro when it has no free version is super heavy.

This pull request has conflicts, please resolve those before we can evaluate the pull request.

should we also block the use of the ResponsiveChartContainer?

The ResponsiveChartContainer and ChartContainer are not exported by the @mui/x-charts-pro 👍